-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(CAT-1226) - Remove Compatibility for Puppet 7.10 and below #73
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had hoped you'd take #68 as a base.
Apologies... I was actually in the process of commenting on your PR as your comment popped up on this! I was rather silly and hadn't checked for other PRs before commencing the work. Looking to incorporate most of the changes you have in your PR into this one so happy to collaborate |
#68 (comment) did raise a valid concern with my approach. I think #67 would be better to merge first. I just rebased it and updated it to make RuboCop pass. Let's see if CI agrees. |
fc65ffe
to
7a27b79
Compare
7a27b79
to
b58bb47
Compare
8e93334
to
79c7724
Compare
@ekohl is there any particular reason you opted to setting minimum compatible puppet version to 7.11? We need to support all versions of the two most recent major releases, so will probably need to reduce the minimum supported puppet version to 7.0. |
Why do you need to support 7.0? That version is dead and won't receive updates anymore? Even the CAT team doesn't support it in most of Puppetlabs modules because it doesn't support the array datatype for exec commands. |
@jordanbreen28 I'd still merge #67 first and not include it here. The PR is already hard enough to review, so that's why I split it up. As for the minimum version, it's for the @bastelfreak does raise a point that Puppetlabs itself already takes 7.9 as a lower bound, even if they don't acknowledge it. Like in puppetlabs/puppetlabs-apache@186c729 I had to make it explicit and my comment in puppetlabs/puppet-lint#142 (review) was ignored when merging it (that check was reverted, so doesn't apply anymore). |
@bastelfreak @ekohl I'm going to raise this internally, I'll update the thread when I've more info! That sounds good to me @ekohl , I'll work to get #67 merged and this PR rebased onto it. |
662e7d9
to
902fb76
Compare
0a353c8
to
c56bb2b
Compare
@bastelfreak @ekohl thanks for your help with this one, we've decided to go ahead and add compatibility from 7.11.0 onwards. |
1cd59c2
to
dd67eb2
Compare
c135d77
to
ef01d40
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I get the impression you took my commit and claimed ownership of it by resetting the author. I'm assuming this is a mistake, rather than intentional but please make sure my original authored code is properly attributed in the git history.
Authoring got lost somewhere in the rebasing. I am working to fix this. |
ef01d40
to
69cfcd7
Compare
@ekohl I hope thats fixed now, apologies! |
69cfcd7
to
6777480
Compare
This avoids the need to have any version specific code and it's the only thing that's testing in CI.
6777480
to
dfb8286
Compare
dfb8286
to
948f39b
Compare
The setting got removed in rspec-puppet 4: puppetlabs/rspec-puppet#73
These settings where used for compatibility with Puppet 7.10 and older (Puppet 7.10 was released more than 2 years ago). rspec-puppet 4 removed them: puppetlabs/rspec-puppet#73 In order to avoid this kind of accident in the future, add an upper bound on the rspec-puppet dependency. Version 5.0.0 is also working with this change, so accept anything before 6.0.0.
Summary
This PR:
Additional Context
Contains commits from #68, thanks to @ekohl.
Checklist